Repository navigation
docs(fork): anchor Send cases, fleet-route trust notes, host kit is out - #736
Merged
Merged
Conversation
- anchor-machine: Send also refuses when the preferred machine has no usable provider or no recent CPU/memory reading; Send picks the machine again before it sends; a thread on a linked machine is not stranded (#47) - fleet-route README: the failed-route branch is wider than the trust rule; public projects and projects with a hosted label put it there (#58) - fleet-route action.yml/README: say what the watch output means (#59) - fleet-route README, fork-fleet.md: static pools need "Run workflows from fork pull requests" off and removal before going public (#62) - gate-trust: the host install kit is in the fork (fork-kit/gh-apps) (#79) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
added a commit
that referenced
this pull request
Nov 21, 2026
…ut (#736) - anchor-machine: Send also refuses when the preferred machine has no usable provider or no recent CPU/memory reading; Send picks the machine again before it sends; a thread on a linked machine is not stranded (#47) - fleet-route README: the failed-route branch is wider than the trust rule; public projects and projects with a hosted label put it there (#58) - fleet-route action.yml/README: say what the watch output means (#59) - fleet-route README, fork-fleet.md: static pools need "Run workflows from fork pull requests" off and removal before going public (#62) - gate-trust: the host install kit is in the fork (fork-kit/gh-apps) (#79) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
added a commit
that referenced
this pull request
Nov 21, 2026
…ut (#736) - anchor-machine: Send also refuses when the preferred machine has no usable provider or no recent CPU/memory reading; Send picks the machine again before it sends; a thread on a linked machine is not stranded (#47) - fleet-route README: the failed-route branch is wider than the trust rule; public projects and projects with a hosted label put it there (#58) - fleet-route action.yml/README: say what the watch output means (#59) - fleet-route README, fork-fleet.md: static pools need "Run workflows from fork pull requests" off and removal before going public (#62) - gate-trust: the host install kit is in the fork (fork-kit/gh-apps) (#79) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
scuttletoby
added a commit
that referenced
this pull request
Nov 21, 2026
…ut (#736) - anchor-machine: Send also refuses when the preferred machine has no usable provider or no recent CPU/memory reading; Send picks the machine again before it sends; a thread on a linked machine is not stranded (#47) - fleet-route README: the failed-route branch is wider than the trust rule; public projects and projects with a hosted label put it there (#58) - fleet-route action.yml/README: say what the watch output means (#59) - fleet-route README, fork-fleet.md: static pools need "Run workflows from fork pull requests" off and removal before going public (#62) - gate-trust: the host install kit is in the fork (fork-kit/gh-apps) (#79) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Docs-only fixes for four fleet and anchor-machine doc issues, plus the leftover from #79. Each one was checked against the current code on main first.
docs/fork/anchor-machine.md. The "Preferred machine offline or busy" row now also covers a preferred machine with no usable provider (not installed, signed out, in error, unavailable, or turned off for the project;useDraftEnvironmentRouting.tscandidate filter) and one with no recent CPU/memory reading (load-balancing.ts, 15 s freshness). It also names "Checking machine resources" (shown while the check runs) and Auto balance unavailable (shown when the reading cannot be fetched). The row about a referenced thread after the move now covers the linked-machine case:threadContextsOutsideEnvironmentskips linked environments, so Send goes ahead. Two optional nits from the review are done too: projectless threads start on the primary machine whenever it offers a "No project" folder, and the open-fails example now says "can settle".runs-onfallback (route job failed) is now called out as wider than the trust rule. It does not checktrusted, bots,privateorhosted, so a dependency bot's pull request from this repository gets the self-hosted label. Public projects, and any project with ahostedlabel, should put the hosted label there instead. Only a private project with"hosted": falseneeds a self-hosted label (the README's example is one). The expression itself is unchanged;fleet_route.test.pystill evaluates it.action.ymland README. Thewatchoutput now says what it means:truewhen at least one job went to a dispatcher or static pool. Nothing starts on it by itself; a project that has its own watch job can use it as that job's condition, as the fork'sfork-tests.ymlfleet_watchdoes. This matchescmd_route(watchis true when any job got a label list rather than the hosted string)..github/fork-fleet.md. On a private repository with static pools: keep "Run workflows from fork pull requests" off, and remove the static runners (or their registration) before the repository is made public. The router cannot stop a workflow file from naming those labels.docs/fork/gate-trust.md. Steps 4 and 5 and "The host" no longer say the host install kit is "not available yet". It shipped in fork-kit/gh-apps: host install kit for GitHub App tokens (gate-trust PR 3) #86 asfork-kit/gh-apps, and it is on theci-releasebranch. The step 4 command now uses the real path (theKIT_PATHplaceholder is dropped from the table). The text says the bootstrap accepts only aci-releasecommit and prints the download and file hashes, mentions--gh-path, and says old agent key files are reported, not imported.Where code and issue differ (followed the code)
refreshBeforeSend, upstream PR fix(web): auto-balanced drafts recheck machine load before sending pingdotgg/t3code#35658). That pick only uses machines that can read every referenced thread, and it ignores links. So the referenced-thread row now says: without a file, Send moves the draft to the thread's machine when that machine qualifies, and otherwise refuses with "Choose a machine to continue". With a file attached, or after a hand pick, Send refuses with "Attached thread is on another machine", unless the machines are linked. A short paragraph after the table explains the re-pick. With the recommended setup, it refuses rather than send to a Manual only machine.General vs project
action.ymlchanges (fleet-route README: failed-route fallback is wider than the trust rule #58, fleet-route action.yml: 'watch' output text implies a job starts by itself #59, fleet docs: static pools need fork-PR workflows off and removal before going public #62) apply to every project that uses thefleet-routeaction, and the matchingfork-fleet.mdparagraph applies to every user of the router.docs/fork/anchor-machine.md(anchor-machine doc: two table rows miss Send-refusal and linked-machine cases #47) describes this app's load-balancing behaviour.docs/fork/gate-trust.md(Owner question: make new agent App keys during the install? #79) is the fork's own owner runbook for the review gate and the host kit.Checks
fork-ci/actions/fleet-route/fleet_route.test.py: 13 tests OK (it reads the README's config andruns-onexpression)..github/scripts/fork-gate-trust-docs.test.py: all passed, 86 ok (it runs the page's step 4 block for real).node .github/scripts/fork-seam-check.cjs --config-ref origin/main origin/main HEAD: OK, fork docs only.Closes #47
Closes #58
Closes #59
Closes #62
🤖 Generated with Claude Code